CA ARCserveĀ® D2D r16.5 Update 1 Release Notes
1.0 Welcome
2.0 Enhancements
3.0 Issues Fixed
4.0 Known Issues
5.0 Limitations
6.0 Installation
6.1 Prerequisite Tasks
6.2 Installation Instructions
7.0 Contact Arcserve
1.0 Welcome
Welcome to the CA ARCserve D2D r16.5 Update 1 Release
Notes. This Release Notes contains important information
about this update.
2.0 Enhancements
The following enhancements have been added to CA ARCserve
D2D for this update:
3.0 Issues Fixed
This update fixes the following issues, which could have
occurred:
- A problem where not all Microsoft Exchange emails are
displayed when expanding a recovery point after generating
a GRT catalog from a CA ARCserve D2D backup of Microsoft
Exchange 2003 or Microsoft Exchange 2007. After you apply
this fix, run a new backup with GRT enabled. (Test Fix
T2D2978)
- A problem that causes a CA ARCserve D2D backup to fail with
error code 64 and the following message: "Can't find file:
error=64,trying to find .VHD file
CDescFile::AddMetaDataSection: WriteFile failed. err[6]".
(Test Fix T5LE123)
- A problem that causes a backup to a NAS device to fail with
a WriteDisk error in the Backup log and the following error
message in AFStor.log “FATAL ERROR! There are 512 bytes of
data left unwritten”. (Test Fix T5LE122)
- A problem that always causes CA ARCserve Central Host-Based
VM Backup to perform a full backup even though an
incremental backup was specified. The following entries are
logged in to the backup log: "Disk XXX size changed,
DiskSize=167040034816, NewDiskSize=167040035328" and "Do
full backup for disk XXX because it is newly added or its
size changed." (Test Fix T2D2954)
- A problem that causes a backup job to fail at the end of
the job while trying to collect disaster recovery
information. The following message is displayed in the
backup-*.log file: "[AFBackupEntryLocalD2D]: [Shrink CHK]
[Collect DR information] Volume size has been changed,
current session will be deleted and next backup will be
converted to verify." (Test Fix T36A800)
- A problem that causes a CA ARCserve D2D Backup Exchange
node job to crash if it is time to purge the transaction
log. (Test Fix T2D2964)
- A problem that causes an incorrect backup type in the
backup xml file. All CA ARCserve D2D backups show as
incremental backups even though a full backup does exist.
This problem is caused by an incorrect backup type in
BackupInfo.xml under the full backup session, which
prevents full backups to display on the CA ARCserve D2D
home page. After you apply this fix, run a new merge job to
correct the BackupInfo.xml file. (Test Fix T2D2966)
- A problem in Cloud Configuration for a copy job, that
causes the "Test Connection" to fail if the proxy server
uses the Basic method for authentication. The following
error message is recorded in Azure.log:
"CAAzureUtils.processStorageException - StatusCode:407
Error Code: ServiceBadResponse Error Message:Proxy
Authentication Required Access Denied" (Test Fix T245831)
- A problem where some virtual machines that perform backup
from CA ARCserve Central Host-Based VM Backup receive the
following warning message: "Could not get volume
information from virtual machine guest OS". The result of
this is that the catalog is not created for the VM, and
therefore file level restores are not possible. (Test Fix
T2D2971)
- A problem that prevents a bare metal recovery for a
Microsoft Windows Server 2012 server with UEFI from
automatically generating a default volume (recovery
partition) in Advanced mode. (Test Fix T5TM103)
- A problem that causes a merge to fail with error 31 when
recovery points reside on certain NAS devices. (Test Fix
T5E5198)
- Data Corruption tool: The data corruption detection utility
(AFUtil.exe) performs a full scan of your recovery points
to confirm the integrity of the backed-up data. For more
information about this problem and the use of the data
corruption detection utility, see the Recovery Point Merge
Failure May Render Recovery Point Unrecoverable topic in
the CA ARCserve D2D online help. (Test Fix RO57870)
- A problem when you create a policy in [assign the value for
egcm in your book] and you set the File Copy settings to
the Amazon S3 cloud destination, the bucket name on the
cloud does not contain a prefix after the policy is
assigned to each CA ARCserve D2D machine. This issue can
cause two different CA ARCserve D2D machines copying the
data to the same bucket. After you apply this fix, create a
policy and deploy it to all CA ARCserve D2D machines. (Test
Fix T2D2961/RO58326)
- A problem where a file copy catalog synchronization job
from the Cloud takes a long time to complete. This fix uses
multithreading to synchronize the catalog which improves
the performance. The default thread number is 8 and the
maximum value is 10. You can change the thread number by
creating a DWORD value ThreadForCatalogSync under:
HKEY_LOCAL_MACHINE\SOFTWARE\CA\CA ARCserve D2D\AFArchiveDll
For more information, see Configure File Copy Settings to
Optimize Performance. (Test Fix T2D2982)
- A problem that causes files under the D2D\BIN folder to be
deleted unexpectedly if the check license task fails in a
copy recovery point job. (Test Fix T5E5203)
For all issues fixed in this release, see the CA ARCserve
D2D r16.5 Release Notes.
4.0 Known Issues
The following issues could exist in this update:
- If the backup destination is a deduplicated-enabled NTFS
volume on Windows Server 2012, and CA ARCserve D2D is
installed on Windows 2003 or Windows XP, restore, merge, or
catalog jobs can fail. The job fails with Windows error
code 50 and message "The request is not supported".
Symptom
McAfee or another third party software set EnableECP=1 in
the registry when they are installed on Windows Server 2012.
Solution
In the registry, change the value of EnableECP from 1 to 0
under the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanManServer\Parameters
For more information, see http://support.microsoft.com/kb/2817216.
- Unable to boot the server after performing a BMR.
Symptom
When the source machine is an Active Directory server
performing a BMR to a physical machine with different
hardware or to a virtual machine on a hyper-v server, the
server does not boot and a blue screen displays with the
following message:
STOP: c00002e2 Directory Services could not start because
of the following error: a device attached to the system is
not functioning. Error status: 0xc0000001.
Solution
Reboot the system to the BMR PE environment, rename all
*.log files in the C:\Windows\NTDS folder, and restart the
system. For example, rename the file edb.log to edb.log.old
and restart the system.
For all known issues in this release, see the CA ARCserve
D2D r16.5 Release Notes.
5.0 Limitations
The following limitations could exist in this update:
- CA ARCserve D2D requires the file attribute "system" to
convert the backup destination folder to the ARCserve D2D
View. However, on some NAS filers, the file attribute
"system" is not supported, therefore you cannot change the
destination to the ARCserve D2D View.
For all limitations in this release, see the CA ARCserve
D2D r16.5 Release Notes.
6.0 Installation
The following sections provide information about
installation prerequisites and installation instructions.
6.1 Prerequisite Tasks
Consider the following prerequisite tasks before installing
this update:
- Before you install this update, verify that CA ARCserve D2D
r16.5 is installed.
6.2 Installation Instructions
You can use two methods to install this update:
Note: The D2D probe is available for download and
installation from the Nimsoft Internet Archive.
7.0 Contact Arcserve
Contact Arcserve Support
For your convenience, Arcserve provides one site where you
can access the information that you need for your Home
Office, Small Business, and Enterprise Arcserve products.
At http://arcserve.com/support, you can access the
following resources:
- Online and telephone contact information for technical
assistance and customer services
- Information about user communities and forums
- Product and documentation downloads
- Arcserve Support policies and guidelines
- Other helpful resources appropriate for your product
Providing Feedback About Product Documentation
If you have comments or questions about Arcserve product
documentation, you can send a message to techpubs@arcserve.com.
Copyright © 2013 Arcserve. All rights reserved. All
trademarks, trade names, service marks, and logos
referenced herein belong to their respective companies.